Fix Python release workflow #102
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes significant changes to the GitHub Actions workflow for building, publishing, and releasing a Python package. The most important changes involve renaming and restructuring jobs, adding steps to store distribution packages, and implementing a new job for signing and uploading releases to GitHub.
Changes to job names and structure:
.github/workflows/python-package.yaml: Renamed thereleasejob tobuildand added dependencies between jobs for better workflow organization.Addition of steps for storing distribution packages:
.github/workflows/python-package.yaml: Added steps to thebuildjob to store the distribution packages using theactions/upload-artifact@v4action.New job for publishing to PyPI:
.github/workflows/python-package.yaml: Introduced a newpublish-to-pypijob that depends on thebuildjob, which handles publishing the package to PyPI.New job for signing and uploading releases:
.github/workflows/python-package.yaml: Added agithub-releasejob that signs the distribution packages with Sigstore and uploads them to a GitHub Release. This job depends on thepublish-to-pypijob.